-
Notifications
You must be signed in to change notification settings - Fork 8.2k
tracing: add gpio tracing capabilities and sample #74199
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Hello @alexanderlayTT, and thank you very much for your first pull request to the Zephyr project! |
aed884f to
94e9b5a
Compare
6184e72 to
fe8af7c
Compare
2cbaac5 to
48cf5c4
Compare
cccfec0 to
b216d18
Compare
7ef7d0f to
3b5c6c2
Compare
490b3d3 to
33f55a7
Compare
5b63e87 to
7d9f428
Compare
|
@alexanderlayTT - there is still a doc build issue You should be able to reproduce with this |
7d9f428 to
77fab01
Compare
77fab01 to
8813ecf
Compare
|
Looks good 👍 Thanks for the attention to detail @alexanderlayTT |
subsys/tracing/user/tracing_user.c
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a way to make the CI not complain about these, especially when the function is empty and __weak?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe this?
/* clang-format off */
...
/* clang-format on */
I don't expect that this needs to be added in this PR, since it's following the same convention used by existing code. However, having compliance failures means that only certain project members with extra privileges can merge this PR.
@nashif - what are you thoughts?
This question was already raised in a previous review comment.
outdated / comments addressed.
|
ping @bjarki-andreasen for a re-review |
bjarki-andreasen
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, nice work!
include/zephyr/drivers/gpio.h
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why not use the macros? for example:
SYS_PORT_TRACING_OBJ_FUNC_ENTER(gpio_pin_interrupt_configure, pin, flags)
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pushed a change to address this - PTAL
If GPIO tracing is enabled, then the system will track various GPIO pin events. Signed-off-by: Alexander Lay <[email protected]> Signed-off-by: Yang Xu <[email protected]>
Implement a sample app to perform basic GPIO tracing. Signed-off-by: Alexander Lay <[email protected]> Signed-off-by: Yang Xu <[email protected]>
532d6ac
8813ecf to
532d6ac
Compare
|
|
||
| static inline int z_impl_gpio_port_get_raw(const struct device *port, | ||
| gpio_port_value_t *value) | ||
| static inline int z_impl_gpio_port_get_raw(const struct device *port, gpio_port_value_t *value) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
such formatting changes should be in a separate commit
|
Hi @alexanderlayTT! To celebrate this milestone and showcase your contribution, we'd love to award you the Zephyr Technical Contributor badge. If you're interested, please claim your badge by filling out this form: Claim Your Zephyr Badge. Thank you for your valuable input, and we look forward to seeing more of your contributions in the future! 🪁 |
If GPIO tracing is enabled, then the system will track input, output, interrupt attachment/removal and interrupt execution for GPIO pins.